Can you provide the debug log when the switch turns off by itself?

See https://www.zigbee2mqtt.io/guide/usage/debug.html on how to enable debug logging.

I thought I did, here for an other device, off at 15:29:31, turned on by automation 15 seconds later, 15:29:46

info  2022-03-01 15:29:31: MQTT publish: topic 'zigbee2mqtt/waterkoker', payload '{"child_lock":"UNLOCK","current":0,"energy":3.11,"indicator_mode":"off/on","linkquality":83,"power":0,"power_outage_memory":"on","state":"OFF","update":{"state":null},"update_available":null,"voltage":237}'
debug 2022-03-01 15:29:31: Received Zigbee message from 'waterkoker', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"rmsVoltage":0}' from endpoint 1 with groupID 0
info  2022-03-01 15:29:31: MQTT publish: topic 'zigbee2mqtt/waterkoker', payload '{"child_lock":"UNLOCK","current":0,"energy":3.11,"indicator_mode":"off/on","linkquality":83,"power":0,"power_outage_memory":"on","state":"OFF","update":{"state":null},"update_available":null,"voltage":0}'
debug 2022-03-01 15:29:31: Received Zigbee message from 'waterkoker', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"rmsVoltage":0}' from endpoint 1 with groupID 0
info  2022-03-01 15:29:31: MQTT publish: topic 'zigbee2mqtt/waterkoker', payload '{"child_lock":"UNLOCK","current":0,"energy":3.11,"indicator_mode":"off/on","linkquality":80,"power":0,"power_outage_memory":"on","state":"OFF","update":{"state":null},"update_available":null,"voltage":0}'
debug 2022-03-01 15:29:31: Received Zigbee message from 'waterkoker', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"53249":4}' from endpoint 1 with groupID 0
debug 2022-03-01 15:29:31: No converter available for 'TS011F_plug_1' with cluster 'manuSpecificTuya_3' and type 'attributeReport' and data '{"53249":4}'`

`debug 2022-03-01 15:29:38: Received Zigbee message from 'waterkoker', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"53249":0}' from endpoint 1 with groupID 0
debug 2022-03-01 15:29:38: No converter available for 'TS011F_plug_1' with cluster 'manuSpecificTuya_3' and type 'attributeReport' and data '{"53249":0}'
debug 2022-03-01 15:29:38: Received Zigbee message from 'waterkoker', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"rmsVoltage":236}' from endpoint 1 with groupID 0
info  2022-03-01 15:29:38: MQTT publish: topic 'zigbee2mqtt/waterkoker', payload '{"child_lock":"UNLOCK","current":0,"energy":3.11,"indicator_mode":"off/on","linkquality":72,"power":0,"power_outage_memory":"on","state":"OFF","update":{"state":null},"update_available":null,"voltage":236}'`

`debug 2022-03-01 15:29:46: Received MQTT message on 'zigbee2mqtt/waterkoker/set' with data 'ON'
debug 2022-03-01 15:29:46: Publishing 'set' 'state' to 'waterkoker'
info  2022-03-01 15:29:46: MQTT publish: topic 'zigbee2mqtt/waterkoker', payload '{"child_lock":"UNLOCK","current":0,"energy":3.11,"indicator_mode":"off/on","linkquality":83,"power":0,"power_outage_memory":"on","state":"ON","update":{"state":null},"update_available":null,"voltage":236}'
debug 2022-03-01 15:29:46: Received Zigbee message from 'waterkoker', type 'attributeReport', cluster 'genOnOff', data '{"onOff":1}' from endpoint 1 with groupID 0
info  2022-03-01 15:29:46: MQTT publish: topic 'zigbee2mqtt/waterkoker', payload '{"child_lock":"UNLOCK","current":0,"energy":3.11,"indicator_mode":"off/on","linkquality":76,"power":0,"power_outage_memory":"on","state":"ON","update":{"state":null},"update_available":null,"voltage":236}'`

I don't see any request send from z2m that turns of the device; so there are 2 possibilities left:

• the plug turns off by itself
• another device in your network turns off the plug, this can be checked via sniffing: https://www.zigbee2mqtt.io/advanced/zigbee/04_sniff_zigbee_traffic.html#with-cc2531

I have a very similar scenario. I have 5 TS011F, all slightly different (different LED light colours, labelling etc) identifying as either TS_011F_plug_1 or TS_011F_plug_3. At first I thought everything was fine, but then one started randomly turning off. Now another two (including the one hosting my internet and zigbee2mqtt and HA services) has started doing the same, so I now have 3 of the 5 doing it. another has a different problem, so am not using, and the 5th reports as 'plug_1' and is the only one that appears to be completely stable. Sorry I have no answer to give, but am definitely interested and thought I would share. I've seen a few other threads with similar issues elsewhere.

Interestingly enough, I have 4 TS011F_plug_3 plugs and as of yesterday one of them started to show the same behaviour. I already tried resetting it but the same happens after disconnecting it from the zigbee network and switching on the plug using the built in hardware button. It looks like it stays on as long as nothing is plugged in, but of course that's not very useful.
When it first happened the plug was providing 2500w for a certain time so I thought maybe it overheated and switched itself as a result of a built in protection mechanism or something but now it shuts off also at more modest wattages so I'm not sure what it could be. It's definitely not being controlled by another zigbee device because it also switches off when not connected to any network. It's also irregular; sometimes it's after 15 minutes, sometimes it stays on for an hour... Hopefully the other plugs won't be next .

I have reported a very similar issue, see #11500. I have some TS011F_plug_1 plugs that behaves exactly the same as yours, and I have some other TS011F_plug_3 that does not show this issue at all.

As far as I understand, the affected variants may have an issue reading the voltage: when the measured voltage drops to 0, the plug disconnect the load. Remember that "voltage" is the input voltage, not the output voltage (which depends on the load switch being open or close). I monitor several appliances in my home, all in the same circuit branch, and only TS011F_plug_1 plugs report temporary drop to 0V in voltage.

My guess is that's a firmware issue, do any of you guys know if the firmware can be upgraded somehow?

Thanks for the response. I have a spare one that I just plugged in the socket, without load. After a couple of days, that one is still on. I will try again with load, but not connected to zigbee.

I don't have a tuya bridge and don't know if there is any update available.

Yes I did the same test, mine stayed on all night and morning without a load and connected to a z2m network. At 9 this morning I plugged in a load and it switched off around noon, ever since then I switch it on manually when I notice it went off but it always goes off again after 15-60 minutes, same behaviour when not connected to a zigbee network. I tried with this setting but to no avail

I'm not sure how to check the firmware version of these, I don't have a tuya bridge either.

Having the exact same issue. I have 3 TS011F_plug_1 and 3 TS011F_plug_3. The plug_3 devices work fine, never go off, the plug_1 randomly turn off.

Still ON:
debug 2022-03-03 22:02:22: Received Zigbee message from 'camera_stijn_switch', type 'attributeReport', cluster 'seMetering', data '{"currentSummDelivered":[0,493]}' from endpoint 1 with groupID 0
info 2022-03-03 22:02:22: MQTT publish: topic 'zigbee2mqtt-meter-pi/camera_stijn_switch', payload '{"current":0.02,"energy":4.93,"linkquality":98,"power":4,"power_outage_memory":"on","state":"ON","voltage":235}'

Going Off:
debug 2022-03-03 22:03:15: Received Zigbee message from 'camera_stijn_switch', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0
info 2022-03-03 22:03:15: MQTT publish: topic 'zigbee2mqtt-meter-pi/camera_stijn_switch', payload '{"current":0.02,"energy":4.93,"linkquality":98,"power":4,"power_outage_memory":"on","state":"OFF","voltage":235}'

Same problem here with a fresh TS011F_plug_1. It works for 3/4 days then goes off. Last time, in the night (according history) while there was no activity on it.

Also running into this problem. I'm running the latest firmware, so perhaps it's a bug in that?

Same here with a TS011F_plug_3 (_TZ3000_typdpbpg). No logs unfortunately as it happened to happen with the exact plug that's powering my server 🤦🏻 . Also one of the plugs was manufactured with a defect so it immediately tripped the ground breakers, might be worth warning for on the docs for these cheap plugs..

Also running into this problem. I'm running the latest firmware, so perhaps it's a bug in that?

Did you update them yourself? With a (tuya) bridge? Maybe we can download that firmware with the manual provided on the z2m website here

Also running into this problem. I'm running the latest firmware, so perhaps it's a bug in that?

Did you update them yourself? With a (tuya) bridge? Maybe we can download that firmware with the manual provided on the z2m website here

I installed the updates that were showing up in zigbee2mqtt, I've never had them tied into a Tuya bridge.

If the device is supporting Over Current Alarm it can being implanted by tuya attribute 0x8003 and its possible see if its the protection that is shutting it down.

If the device is supporting Over Current Alarm it can being implanted by tuya attribute 0x8003 and its possible see if its the protection that is shutting it down.

How to do this?

@MattWestb just to provide a bit of skepticism to that: I've been able to run my oven's cleaning cycle without any random shutoffs (~2.9kW sustained), but I'll get random shutoffs in the middle of the night when there's no electrical load to speak of (<5W)

I have a watchdog automation that keeps things running, but the pattern to the shutoffs makes me think that it's something other than overcurrent protection being tripped.

@nickles-lee I dont have the device but i knowing tuya have implanted the attribute is some device and if the device is supporting it i think its good to knowing if its shutting down for protection. Also some user looks only having problem then they is having load on the device but it can being hardware problems and also firmware that is making the bad thing but in the end its can helping implanting the attribute and returning the device to the seller if its being triggered and the max load is not being used.

I don't know if it can help. I noticed while looking at the history that the socket does not only turn off, it also reports when this happens a voltage equal to 0 (A normal switch off doesn't change voltage)

@navycrow Its sounds like over current protection is disabling the output then its zero V.
Only way to knowing it is implanting the tuya attribute 0x8003 and you can getting it reported if its happens.
I think its not the same problems for all users but i think some is have the problems with the over current protection.

Maybe but personally, I don't really believe in this hypothesis. In my case, the socket always cuts when it does not work.

I have the same problem with the ts011f_plug_1. Cut off power randomly.

Me too...

Also running into this problem. I'm running the latest firmware, so perhaps it's a bug in that?

Did you update them yourself? With a (tuya) bridge? Maybe we can download that firmware with the manual provided on the z2m website here

I installed the updates that were showing up in zigbee2mqtt, I've never had them tied into a Tuya bridge.

For both my devices, there are no z2m ota updates available. I have _TZ3000_u5u4cakc (TS011F_plug_3) and _TZ3000_typdpbpg (TS011F_plug_1), running z2m 1.24.0-dev commit: [42f229b]

I have the same issue. See video on dropbox showing socket turning off by itself 2 times.

So, as a first step I removed 2 of my 3 Tuyas from the socket to see if they where somehow interfering with each other. That was not the case, the last one still turned off. Then I removed the last one from my ZigBee network to see if that does anything. Still turning off after a day or so.

The only way to use them now is to make an automation in HA and not having them connected to a critical system

I complained to the Aliexpress seller. He consulted Tuya who told him that a Tuya hub was needed for it to work properly. I don't believe it but to remove the doubt, I bought one and paired the sockets on it (4). For the moment none, after 1 day no socket has cut. On the other hand, I notice in the Tuya Smart Life application that the socket has Error parameters (OV_CR, Over voltage, Over power, Under current, Under voltage, under power). I don't if they are hard encoded in the socket itself. Can this be integrated into Z2MQTT??

Can you remove one of the sockets from the Tuya bridge to see if that introduces the issue again?

In my opinion it shouldn't matter which bridge is being used because they are turning off when there is no bridge as well. Maybe there is some keepalive mechanism in place between the original Tuya bridge and the sockets?

Hey! I think i found solution for that issue. You need Zigbee/Tuya gateway. Disconnect that smart plug from z2m and connect it via gateway and Your Tuya/SmartLife app. Then start updating firmware. After succesfully update re-pair with z2m again and that`s all. It should work (at least in my case is working perfectly!).

i buyed 8 and updated them and no power off for weeks now :)

just update OTA from Z2M and it works. they will be firmware 1.13 and they work really good. no issues at all for weeks now
If they still have an issue, your plug is probably faulty..

Many of us have already updated to 1.0.13 and problem with powering off with voltage 253V and higher.

Many of us have already updated to 1.0.13 and problem with powering off with voltage 253V and higher.

what socket u have then ?
There are many of them on Aliexpress only one specific one works, i did buy them all and all of them besides 1 socket does work on 1.0.13

This one is 20a
I'm using fridges, tv's, freezers, terrariums, washmachine, on the sockets, all work fine.
So i decided to buy all available sockets from the supplier.

the thing i did notice they work as a router, so all my router usb sticks are useless now, as this extends my network with 90 signal

The update is not available for this plug on (tuya/smartlife app) u need to update trough zigbee2mqtt.

@Koenkk : One of my plugs (a round one, blue color, TZ3000_gjnozsaz) switched OFF today.
I did never switch OFF before, in about a month, and has firmware 1.0.13. The mains voltage did not go over 250 Volt.

this is the log:
info 2022-07-22 13:19:08: MQTT publish: topic 'zigbee2mqtt/TuyaPlug4', payload '{"child_lock":"UNLOCK","current":11.41,"energy":89.36,"indicator_mode":"off/on","linkquality":63,"power":2647,"power_outage_memory":"on","state":"ON","update":{"state":"idle"},"voltage":229}'
debug 2022-07-22 13:19:13: Received Zigbee message from 'TuyaPlug4', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"rmsCurrent":11765}' from endpoint 1 with groupID 0
info 2022-07-22 13:19:13: MQTT publish: topic 'zigbee2mqtt/TuyaPlug4', payload '{"child_lock":"UNLOCK","current":11.77,"energy":89.36,"indicator_mode":"off/on","linkquality":60,"power":2647,"power_outage_memory":"on","state":"ON","update":{"state":"idle"},"voltage":229}'
debug 2022-07-22 13:19:13: Received Zigbee message from 'TuyaPlug4', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"activePower":2728}' from endpoint 1 with groupID 0
info 2022-07-22 13:19:13: MQTT publish: topic 'zigbee2mqtt/TuyaPlug4', payload '{"child_lock":"UNLOCK","current":11.77,"energy":89.36,"indicator_mode":"off/on","linkquality":60,"power":2728,"power_outage_memory":"on","state":"ON","update":{"state":"idle"},"voltage":229}'
debug 2022-07-22 13:19:16: Received Zigbee message from 'TuyaPlug4', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"53249":1}' from endpoint 1 with groupID 0
debug 2022-07-22 13:19:16: No converter available for 'TS011F_plug_1' with cluster 'manuSpecificTuya_3' and type 'attributeReport' and data '{"53249":1}'
debug 2022-07-22 13:19:16: Received Zigbee message from 'TuyaPlug4', type 'attributeReport', cluster 'genOnOff', data '{"onOff":0}' from endpoint 1 with groupID 0
info 2022-07-22 13:19:16: MQTT publish: topic 'zigbee2mqtt/TuyaPlug4', payload '{"child_lock":"UNLOCK","current":11.77,"energy":89.36,"indicator_mode":"off/on","linkquality":60,"power":2728,"power_outage_memory":"on","state":"OFF","update":{"state":"idle"},"voltage":229}'
debug 2022-07-22 13:19:17: Received Zigbee message from 'TuyaPlug4', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"53249":0}' from endpoint 1 with groupID 0
debug 2022-07-22 13:19:17: No converter available for 'TS011F_plug_1' with cluster 'manuSpecificTuya_3' and type 'attributeReport' and data '{"53249":0}'
debug 2022-07-22 13:19:18: Received Zigbee message from 'TuyaPlug4', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"rmsCurrent":0}' from endpoint 1 with groupID 0
info 2022-07-22 13:19:18: MQTT publish: topic 'zigbee2mqtt/TuyaPlug4', payload '{"child_lock":"UNLOCK","current":0,"energy":89.36,"indicator_mode":"off/on","linkquality":66,"power":2728,"power_outage_memory":"on","state":"OFF","update":{"state":"idle"},"voltage":229}'
debug 2022-07-22 13:19:18: Received Zigbee message from 'TuyaPlug4', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"activePower":0}' from endpoint 1 with groupID 0
info 2022-07-22 13:19:18: MQTT publish: topic 'zigbee2mqtt/TuyaPlug4', payload '{"child_lock":"UNLOCK","current":0,"energy":89.36,"indicator_mode":"off/on","linkquality":69,"power":0,"power_outage_memory":"on","state":"OFF","update":{"state":"idle"},"voltage":229}'
debug 2022-07-22 13:19:18: Received Zigbee message from 'TuyaPlug3', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"rmsVoltage":240}' from endpoint 1 with groupID 0
info 2022-07-22 13:19:18: MQTT publish: topic 'zigbee2mqtt/TuyaPlug3', payload '{"child_lock":"UNLOCK","current":0,"energy":8.83,"indicator_mode":"off/on","linkquality":12,"power":0,"state":"OFF","update":{"state":"idle"},"voltage":240}'
debug 2022-07-22 13:19:18: Received Zigbee message from 'TuyaPlug4', type 'attributeReport', cluster 'seMetering', data '{"currentSummDelivered":[0,8937]}' from endpoint 1 with groupID 0
info 2022-07-22 13:19:18: MQTT publish: topic 'zigbee2mqtt/TuyaPlug4', payload '{"child_lock":"UNLOCK","current":0,"energy":89.37,"indicator_mode":"off/on","linkquality":60,"power":0,"power_outage_memory":"on","state":"OFF","update":{"state":"idle"},"voltage":229}'
debug 2022-07-22 13:19:19: Received Zigbee message from 'TuyaPlug4', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"rmsVoltage":240}' from endpoint 1 with groupID 0
info 2022-07-22 13:19:19: MQTT publish: topic 'zigbee2mqtt/TuyaPlug4', payload '{"child_lock":"UNLOCK","current":0,"energy":89.37,"indicator_mode":"off/on","linkquality":66,"power":0,"power_outage_memory":"on","state":"OFF","update":{"state":"idle"},"voltage":240}'

The debug shows a "No converter available" message, on the moment the plug switched off.
Koen, can you explain what happend here ?

Thanks in advance !!

You have the blue round ones, the orange also have an issue.

buy the 20a Round ones (white).

@meganiekje not sure what the device tries to say with this message, but the 'No converter..' message is definitely not the root cause;

debug 2022-07-22 13:19:16: Received Zigbee message from 'TuyaPlug4', type 'attributeReport', cluster 'manuSpecificTuya_3', data '{"53249":1}' from endpoint 1 with groupID 0
debug 2022-07-22 13:19:16: No converter available for 'TS011F_plug_1' with cluster 'manuSpecificTuya_3' and type 'attributeReport' and data '{"53249":1}'

In tuya dev docs for "normal zigbee devices" is attribute on 0x0006 OnOff Cluster:

• 0x8003 Over Current Alarm (t.Bool) 0/1 (Default 0x00)
  • 0x00 = Over Current OK
  • 0x01 = Over Current Alarm

But i think its one other tuya "extended version" implanted in this devices.

And Z2M have not implanting the over current alarm standard or "extended" version so hard to say but looks like it that.

@MattWestb 0x8003 = 32771 so that doesn't match the 53249 from the message.

= normal for all tuya devices.
Its not the first and the last time tuya dev docks is not the same as the devices is doing in real.

My suggestion is implanting the over current alarm for the TS011F devices

@MattWestb , @Koenkk : I was running my washing machine and the (heatpump)dryer and a fridge on the same plug. I see sometimes some high ampere spikes on the moment the fridge motor starts.
It could be, that the plug measured a current of more than 16 Amps for a very short time.
The 16 Amp (automatic) mains fuse did not trip.

Using the _TZ3000_5f43h46b plugs, on newest available version (Application version 77) but still have issues with powering off randomly.

You have the blue round ones, the orange also have an issue.

buy the 20a Round ones (white).

@malosaa : I'm also looking to get one. Would you mind sharing a purchase link for this 20A sensor ?
Is this the right one : https://www.aliexpress.com/item/1005004370560903.html ?

Thank you.

Hello,

Same problem here:

no voltage spike @ 250v it still shut down

Using ZHA.

You have the blue round ones, the orange also have an issue.

buy the 20a Round ones (white).

can you give a link to us? thanks

I tested the tz3000_typdpbpg square plugs today with deCONZ (ConBee II USB stick) and it's the same: keeps shutting off regularly. I believe deCONZ should have updated the firmware by itself? OTA updates are at least enabled in the PhosCon GUI. However, I cannot check the voltage measurement, since Home Assistant or deCONZ cannot read the voltage, current, or power reading of the plug, unfortunately.

Does anyone have a Tuya gateway and could try to capture traffic to a plug via zigbee explorer or any other means ?
Given how they turn off af the same time, i don't think its a bug, it's a Tuya "feature" for us as award for not using their gateway...
There must be some kind of heartbeat sent in the background. If we know what it is, we could try to mimic it using automation...

I'm actually completely fed up with this Tuya-almost-monopoly in this category of devices. The WiFi plugs, dimmers, and switches that used to be convertible to Tasmota firmware are more and more difficult to find. The tuya ones connect to their master's server by themselves, over your wifi network. Zigbee devices used to be independent of that, but now apparently their firmware is putting on hurdles to operate without a tuya hub that is undoubtedly calling home in the background. It looks like someone is very focused on invading our homes with hardware that exposes itself to someone outside.
I know that on the Blackadder site, many devices are listed, but many of them have the remark that the newer ones have tuya installed and can no longer be used without.
Wouldn't it be time for an online blacklist of unfavorable devices, and a whitelist of parts (and where to buy them) that are not connecting to some sever in the East?

I'm actually completely fed up with this Tuya-almost-monopoly in this category of devices. The WiFi plugs, dimmers, and switches that used to be convertible to Tasmota firmware are more and more difficult to find. The tuya ones connect to their master's server by themselves, over your wifi network. Zigbee devices used to be independent of that, but now apparently their firmware is putting on hurdles to operate without a tuya hub that is undoubtedly calling home in the background. It looks like someone is very focused on invading our homes with hardware that exposes itself to someone outside. I know that on the Blackadder site, many devices are listed, but many of them have the remark that the newer ones have tuya installed and can no longer be used without. Wouldn't it be time for an online blacklist of unfavorable devices, and a whitelist of parts (and where to buy them) that are not connecting to some sever in the East?

Hello, do not mean to advertise us, but look at our products - for now we have smart plugs and smart power strip with Tasmota already installed from the factory and you can use what you bought without any cloud.
Search for the Nous A1T and Nous A5T.
We also looking to give clients smart wall switches, bulbs and led strips with tasmota or WLED.
So yes, there are companies that see your desires and working on it ;)

Hello, do not mean to advertise us, but look at our products - for now we have smart plugs and smart power strip with Tasmota already installed from the factory and you can use what you bought without any cloud. Search for the Nous A1T and Nous A5T. We also looking to give clients smart wall switches, bulbs and led strips with tasmota or WLED. So yes, there are companies that see your desires and working on it ;)

Hello @Nous-smart-home
I have your power plug Nous A1Z, can you solve issue with powering off with high voltage?
In europe many countries have 230V +/- 10% as normal range, maximum allowed Voltage range for PV generators are up to 264V, but your plugs are not working at all if voltage is around 250V.

Hello, do not mean to advertise us, but look at our products - for now we have smart plugs and smart power strip with Tasmota already installed from the factory and you can use what you bought without any cloud. Search for the Nous A1T and Nous A5T. We also looking to give clients smart wall switches, bulbs and led strips with tasmota or WLED. So yes, there are companies that see your desires and working on it ;)

Hello Nous I have your power plug Nous A1Z, can you solve issue with powering off with high voltage? In europe many countries have 230V +/- 10% as normal range, maximum allowed Voltage range for PV generators are up to 264V, but your plugs are not working at all if voltage is around 250V.

Hello, yes, our sockets turn off at 250V, we know that and its made for the safety reasons, but we also hear a lot request to rise this voltage bar to 260V, and we can do that, the question is, should we? its the question we keep asking ourselfs from time to time, because we do not want to risk your appliances that could act weird or even worse...

Currently we are researching whether its possible to update already sold plugs to the new firmware and 260v bar or no. So I will reply here for you a bit later

@Nous-smart-home If you is selling power plug for the EU market then it shall comply with the EU regulations and no only marking it with CE (marking that any brands from some countries is doing).

Most of the EU counties is having 230V +/- 10% and if selling the same plug to one other country's with 110V or other voltage system (with or without CE marking) its need one other power setting in the plugs firmware (config data) or its not working OK in that country (ref tuya dev docks for calibration the power measurement).

If putting the over voltage to 260V i cant see any EU regulations that is being broken then the plug shall being secured with one flue if to much power (A) is running in to it if getting one short circuit on the load or in the plug.

If one user is getting higher voltage (> 260V) from its power supplier and the load equipment is being broken its one thing for the user taking with the power supplier .
(some EU countries is having not so stable grids and can making problem with EU-Grid before they is disconnecting the local grid from EU-Grid).

Great thanks for trying getting well working devices for the community users that have large problems with many no (real) name devices then have baying and hope some supplier is serious getting devices that is working in the EU and other countries.

Jordan87 - can you confirm that those plugs work well with z2m other then voltage issue ?

@Nous-smart-home - If you want to sold your devices to EU you should change it at least in EU version (probably not possible to differentiate old models with non EU plugs), Not only EU countries have 230V and higher https://www.worldstandards.eu/electricity/plug-voltage-by-country/

Jordan87 - can you confirm that those plugs work well with z2m other then voltage issue ?

With Nous I was facing only issue with high voltage, no other random power off's. I have other brand which was randomly powering off but with old firmware, not 1.0.13 which should solve it.

@Nous-smart-home If you is selling power plug for the EU market then it shall comply with the EU regulations and no only marking it with CE (marking that any brands from some countries is doing).

Most of the EU counties is having 230V +/- 10% and if selling the same plug to one other country's with 110V or other voltage system (with or without CE marking) its need one other power setting in the plugs firmware (config data) or its not working OK in that country (ref tuya dev docks for calibration the power measurement).

If putting the over voltage to 260V i cant see any EU regulations that is being broken then the plug shall being secured with one flue if to much power (A) is running in to it if getting one short circuit on the load or in the plug.

If one user is getting higher voltage (> 260V) from its power supplier and the load equipment is being broken its one thing for the user taking with the power supplier . (some EU countries is having not so stable grids and can making problem with EU-Grid before they is disconnecting the local grid from EU-Grid).

Great thanks for trying getting well working devices for the community users that have large problems with many no (real) name devices then have baying and hope some supplier is serious getting devices that is working in the EU and other countries.

Thank you for understanding that we are trying to help our clients, providing good products and solving their problems with it, but we also do not want to hurt them, so that's where the concerns are going from.
Of course our product passed CE regulations, otherwise we would be able to sell them in EU.
And we encountered this 250+ volts problem this year. We did not hear much about that last or year before that.
So do not worry, we will solve this issue. As told above, we are working on it right now ;)

@Nous-smart-home
Can you push firmware update to my A1Z to increase overvoltage protection in my unit?
Virtual ID: bfab4c0be08babdefbgsus
MAC: a4:c1:38:ed:dc:3a:06:94

My current firmware version is 1.0.13

@Nous-smart-home Can you push firmware update to my A1Z to increase overvoltage protection in my unit? Virtual ID: bfab4c0be08babdefbgsus MAC: a4:c1:38:ed:dc:3a:06:94

My current firmware version is 1.0.13

Unfortunately so far I do not know if we even can update current sockets. We talking with the factory about that. Hope we can, then we will update all of them.

@Nous-smart-home @Jordan87 @MattWestb and all others
Does someone of you know if this 250+ volt problem also effects the A1T version or only the A1Z version from Nous?
I was not sure which one of the two mentioned I should buy and assumed the Zigbee version might consume less power itself (Zigbee vs WLAN). An other advantage is probably a more direct integration in Home Assistant (avoiding additional MQTT). On the other side I stumbled ther problem described here. So which one would you chooose?